feat: Button variant ghost — implements nuri-com/nuri-design-system#233 - #234

Implements #233: Button variant: 'ghost'.

• Admission: decision, Extension, sole-architect exception, with the independent review and the amendment.
• Ready: Project Ready was confirmed by the operator on 2026-10-29. The gh token has no read:project scope, so this PR does not verify it.
• Base: origin/main at 111aaab.

It reverses #154 (08030f6) for Button ghost only. #154's stack fill/distribute and alert hug stay.

Contract delivered

• ButtonProps.variant is now 'solid' | 'soft' | 'ghost'. The default stays soft.
• Ghost composes root.palette.variant: 'ghost': transparent at rest, text-primary text, bg-subtle when pressed.
• Ghost shares everything else with solid and soft: anatomy, sizes (sm 36, lg 60), padding, fill, slots, press scale and disabled opacity.
• accent is accepted on ghost and paints nothing. This is documented, not excluded in the types.
• Anti-scope respected: no palette row, token or CSS; no schema change (the Guard F pin did not move); no size, padding or hitSlop change; IconButton untouched; no amount-switch component.

Changes

A note on "put back the ghost cells". Before #154, only resolve.test.ts had Button ghost cells. render-smoke and type-tests never had one: #154 only repointed md→lg there. geometry-bake derives the cross-product from the descriptor, so it covers ghost automatically. The resolve cells are restored verbatim. The render-smoke, type-test and geometry-bake cells are new.

Verification (commands and output)

All commands were run in a fresh worktree (from origin/main + npm ci) on the tree committed as e5ea0ba.

$ node --test scripts/*.test.js
# tests 128 · pass 128 · fail 0

$ npm test -w @nuri/prototype
# tests 130 · pass 130 · fail 0

$ npm test -w @nuri/doc
# tests 3 · pass 3 · fail 0

$ npm test -w @nuri/rn
Test Suites: 21 passed, 21 total
Tests:       308 passed, 308 total
Snapshots:   26 passed, 26 total        # none written, none updated

$ npm run typecheck -w @nuri/rn          # tsc → exit 0
$ npm run typecheck -w @nuri/expo-demo   # tsc → exit 0

Deterministic re-emit. I ran npm run build && npm run build -w @nuri/doc twice and hashed every file under packages/{rn,prototype,doc,playground}/generated, packages/prototype/styles and packages/spec (163 files) with sha256:

build 1 manifest sha256: 3642cc76fabd03b8959a51be85a84805b84b035abd72839f44cb5f90508333bd
build 2 manifest sha256: 3642cc76fabd03b8959a51be85a84805b84b035abd72839f44cb5f90508333bd
diff → IDENTICAL across two builds

After the builds, git status shows only the three intended generated files changed.

solid and soft are unchanged. There is no diff in packages/rn/__tests__/__snapshots__/, packages/prototype/styles/, packages/playground/generated/ or packages/rn/generated/data/.

Mutation check (the new cells bind). I changed the spec's ghost row to palette: { variant: 'soft' } and rebuilt. resolve and render-smoke then report Tests: 4 failed, 111 passed. After restoring the row and rebuilding, the generated hashes are identical to the pre-mutation manifest.

Web probe (playground component/button.html, computed styles)

• Accent: the board's accent control was set to neutral, lilac and orange, in light and dark. All 6 combinations give identical ghost values.
• CSS: the matched rules are the existing generic ones, .nuri-palette[data-variant="ghost"] { background: transparent; color: var(--nuri-text-primary) } and …[data-press-color]:active { background: var(--nuri-bg-subtle) }.
• Pressed read: to read the pressed end colour, the 0.12s transition was set to none inline on the probe elements only.

RN-web probe (expo-demo expo start --web, Bitcoin tab, computed styles)

• Reference: on the same screen, soft "Receive" is rgb(243,241,226).
• Probe cells: the lg, accent and disabled cells come from a temporary probe block in Bitcoin.tsx. It was not committed, and the file was restored byte-identically (sha256 7f6cb4ae…).
• Pressed read: pressed was read while holding a pointerdown.

Evidence (docs/evidence/button-ghost/)

• web-variant-board-light.png: solid, soft and ghost side by side.
• web-ghost-board-light.png and web-ghost-board-dark.png.
• rn-web-bitcoin-swap-light.jpg: the committed expo-demo screen.
• rn-web-probe-matrix-light.jpg and rn-web-probe-matrix-dark.jpg: the temporary RN-web probe matrix (lg, orange, lilac, disabled).

Not verified

• Native device or simulator. There is no iOS or Android render of ghost and no native pressed or disabled screenshot. RN coverage is react-test-renderer (jest) plus RN-web only.
• Hit target. The check that the 36px sm swap button is easy to hit was not run. It needs a human tap on a device. If it fails, that is a separate request (hitSlop or size), per the decision.
• Pressed screenshots. The pressed state is proven by computed-style reads, not screenshots.
• Independent verification. This is the implementer's run. Independent verification by another session is still required before Verified/Done, and this PR does not self-certify it.

Follow-ups

1. send-wip.html cleanup. It is not on origin/main (it lives on feat/playground-new-recipient-colour), so it is left out here. Once that branch is on main:
   • replace the 7 data-x-ghost … variant="soft" buttons with variant="ghost";
   • delete the two nuri-button[data-x-ghost] rules in <style data-outside-ds>, keeping .xpair, .xrow and the rest;
   • in the AMOUNT VARIANTS intro, say the button is now DS.
2. Playground and expo-demo parity. packages/playground/pages/screens.html has the Bitcoin board that Bitcoin.tsx mirrors. It does not have the ghost swap yet, because that file is outside the admitted scope. Adding the same 4 lines there is an operator call.
3. Expo web bundling fails on main. packages/rn/runtime/native-text-input-command.ts pulls AndroidTextInputNativeComponent into the web graph, which gives "Importing native-only module … on web". The RN-web probe above used the operator-local, untracked native-text-input-command.web.ts shim, copied in temporarily and removed afterwards (it is not in this PR). That fix should land on main separately.
4. Release. Add the release-note line "Button: variant="ghost"" in the next rn/v0.x.y tag. Tagging is the operator's.
5. nuri-expo adoption. That comes after the vendoring sync, as a separate consumer PR.

🤖 Generated with Claude Code